home *** CD-ROM | disk | FTP | other *** search
- Path: walrus.megabaud.fi!not-for-mail
- From: petrin@walrus.megabaud.fi (Petri Nordlund)
- Newsgroups: comp.sys.amiga.applications
- Subject: Re: Executive Probs with Maple
- Date: 19 Jan 1996 18:13:37 +0200
- Organization: Megabaud Oy,Helsinki,Finland
- Message-ID: <4dofvh$p9p@walrus.megabaud.fi>
- NNTP-Posting-Host: walrus.megabaud.fi
-
- W.G.J. Langeveld <wglp09@scsa1.slac.stanford.edu> writes:
-
- >> I have tested Executive only with Maple 1.0, may something was
- >> changed in later versions?
- >
- >You mean the original version of Maple for the Amiga, not Maple V release 3?
- >You betcha it was changed. It was rewritten completely, not a line of code is
- >the same.
-
- Yes, I'm talking about that version.
-
- >> I know this problem and in AddTask() Executive checks if the parent
- >> task is scheduled, and if the new task has same priority, it will be
- >> given the parent task's real priority. The scheduler will adjust the
- >> priority later, but Executive remembers correct task priorities and
- >> can restore them when it quits.
- >
- >Good, that's how it is supposed to work. So you are SetFunction()ing
- >AddTask()?
-
- Yes, and RemTask().
-
- >> But if user lowers Maple's priority below the plotter's, the plotter
- >> will not work anymore.
- >
- >Not true, actually. The plotter will run fine with Maple's priority set
- >lower. That is, it can redraw stuff and rotate, etc. Again, I suspect
- >you're looking at the old version.
-
- With the old version this is true, user can't change the maintask's
- priority below -24.
- --
- __
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~///~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Petri Nordlund __/// petrin@megabaud.fi
- ---------------------------------\XX/----------------------------------
-